Medical equipment servicing

ABSTRACT

Systems and techniques for centralized management and servicing of medical equipment such as automated external defibrillators (AEDs) are described herein.

TECHNICAL FIELD

Systems and techniques for centralized management and servicing ofmedical equipment such as automated external defibrillators (AEDs) aredescribed herein.

BACKGROUND

Sudden health problems such as sudden cardiac arrest and injuries causedby accidents kill thousands of people and cause permanent injury everyyear. Fast and competent care can be essential to positive outcomes insuch situations. For example, it is said that the chance of surviving asudden cardiac arrest falls by ten percent for every minute in delayingeffective treatment.

Emergency events like sudden cardiac arrests and accidents are generallyresponded to by organized emergency response units, such as ambulance orfire crews, and by laypeople who are immediately around the events sothat they personally witness or offer assistance for the events.

SUMMARY

In some aspects, a method includes receiving status updates frommultiple automated external defibrillators, receiving, from a user, arequest to access status information, and sending, to the user, summarylevel status information for at least some of the multiple automatedexternal defibrillators, the summary level status information beinggrouped based on a measure of geographic proximity of the multipleautomated external defibrillators.

Other embodiments of this aspect include corresponding systems,apparatus, and computer programs recorded on one or more computerstorage devices, each configured to perform the actions of the methods.A system of one or more computers can be configured to performparticular actions by virtue of having software, firmware, hardware, ora combination of them installed on the system that in operation causethe system to perform the actions. One or more computer programs can beconfigured to perform particular actions by virtue of includinginstructions that, when executed by data processing apparatus, cause theapparatus to perform the actions.

Other features and advantages of the invention will be apparent from thedrawings, detailed description, and claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a schematic diagram of a system for responding to an emergencymedical condition according to an example embodiment of the invention.

FIG. 2 is a block diagram of a system for managing medical equipmentaccording to an example embodiment of the invention.

FIGS. 3A-B show exemplary screen shots for medical equipment management.

FIG. 4 is a flow chart of a process for providing status informationabout medical equipment according to an example embodiment of theinvention.

FIG. 5 is an exemplary screen shot for medical equipment management.

FIG. 6 is a flow chart of a process for providing software and/orconfiguration updates to medical equipment according to an exampleembodiment of the invention.

FIG. 7 shows an example of a generic computer device and a genericmobile computer device, which may be used with the techniques describedherein.

DETAILED DESCRIPTION

FIG. 1 shows a system 100 for responding to an emergency medicalcondition of a subject 102. In general, system 100 includes variousportable devices for monitoring on-site care given to the subject 102 ofthe emergency situation. A rescuer 114 in this example is interactingwith a computing device in the form of a laptop computer 116 thatincludes a graphical display by which to report information to therescuer 114, and may have an input mechanism such as a keyboard or atouchscreen by which the rescuer 114 may enter data into the system 100.Separately, a portable defibrillator 112 is shown in a deployed stateand is connected to the subject 102. In addition to providingdefibrillation, the defibrillator 112 may serve as a patient monitor viaa variety of sensors or sensor packages. For example, as shown here,electrodes 108 connected to the defibrillator 112 have been applied tothe subject 102 so that electrical shocking pulses may be provided tothe electrodes in an effort to defibrillate the subject 102, andelectrocardiogram (ECG) signals may be read from the subject 102.Further examples of use of the portable defibrillator are described, forexample, in Ser. No. 13/398,280 filed on Feb. 16, 2012 and entitled“Coordinated Resuscitation Perfusion Support”, the contents of which arehereby incorporated by reference.

The defibrillator 112 may include an accelerometer assembly 110configured to identify a vertical displacement caused by CPRcompressions and provide feedback to the rescuer based on the measureddisplacements. The defibrillator can additionally be provided with aventilation bag 104 that includes an airflow sensor 106 to identify arate at which ventilation is occurring with the subject. Thedefibrillator 112 may communicate through a short range wireless dataconnection with the laptop 116 to provide to the laptop 116 statusinformation, such as information received through the electrode assembly108, including ECG information for the subject 102. Also, thedefibrillator 112 can provide information to the rescuer 114 about theperformance of chest compressions, such as depth and rate informationfor the chest compressions. The defibrillator operates according to aset of configurations stored on the defibrillator. The configurationscan include a language setting, a CPR rate setting, a CPR depth setting,a shock voltage, and a shock wave form.

In order for a defibrillator, such as defibrillator 112, to be usefulduring a medical emergency, the defibrillator must be charged andfunctional when the device is needed. In order to ensure thedefibrillators are functional, regular servicing is needed. For example,batteries must be replaced when they no longer store adequate charge topower the defibrillator, electrodes may need to be replaced to ensurethe electrodes will function appropriately, and the like. Additionally,over time software for the defibrillators may be updated based onenhancements or changes to protocols and/or configurations for thedefibrillator may be modified based on changes in various protocols. Assuch, after defibrillator is purchased and installed at a locationregular servicing is needed to ensure that the device will be availableand functional when needed.

FIG. 2 shows a system for communication between medical equipment and adispatch center 214 and a medical equipment management system 216.Medical equipment, e.g., defibrillation devices 200 a-f and first-aidunits 201 a-b are communicatively coupled to the dispatch center 214 andthe medical equipment management system 216.

Communications between the dispatch center 214 and the devices 200 a-fand 201 a-b can be used to alert rescue services upon activation of oneof the devices and/or to communicate with a rescuer when one of thedevices 200 a-f is in use. Such communication between defibrillators anda dispatch center 214 is described, for example, in U.S. patentapplication Ser. No. 12/946,843, filed on Nov. 15, 2010, and entitledCommunity-Based Response System, the contents of which is herebyincorporated by reference in its entirety.

Communications between the medical equipment management system 216 andthe medical equipment (e.g., defibrillation devices 200 a-f and firstaid units 201 a-b) can provide centralized servicing of the medicalequipment. The medical equipment management system 216 can include astatus module 220 and a software update module 218. The status module220 receives status information from medical equipment communicativelycoupled to the medical equipment management system 216, and providescentralized access to this information as described in more detailbelow. The software update module 218 can include information about thesoftware and/or configurations currently stored on various medicalequipment and new software and/or configurations available for themedical equipment. The software update module 218 can additionally send(e.g., push) updates to a particular piece of medical equipment tochange or update the software and/or configurations of the medicalequipment.

More particularly, as shown in FIG. 2, multiple pieces of medicalequipment such as defibrillation devices 200 a-f and first aid units 201a-b can be located in various physical locations. A particular buildingor area may include multiple defibrillation devices or other pieces ofmedical equipment. For example, building 202 includes defibrillationdevices 200 a, 200 b, and 200 c and first aid unit 201 a. Each of thesedevices can be communicatively coupled to the management center 216. Forexample, defibrillation devices 200 a, 200 b, and 200 c and first aidunit 201 a can include a transmitter in communication with a wirelessrouter 206. The wireless router 206 can send messages received from thedefibrillation devices 200 a, 200 b, and 200 c and first aid unit 201 ato an external router 208 and the router can relay the messages to aremotely located server 212 via a cellular network 210. Messages sentfrom defibrillation devices 200 a, 200 b, and 200 c and first aid unit201 a can include information about the status of the medical equipment.For example, the messages can include information such as batterycharging level, date of last servicing, error indications, electrodes orother component expirations, supply shortages and the like. Thesemessages are relayed to the medical equipment and management system 216.Thus, the medical equipment provides messages indicative of their statusto a medical equipment management system 216 and the medical equipmentmanagement system 216 can provide a centralized location for a deviceadministrator to access status information for multiple disparatelylocated devices. Centralized storage and access to information about thestatus of different pieces of medical equipment such as defibrillationdevices can reduce the time and cost associated with servicing medicalequipment because the administrator does not need to physically go tothe devices to check their status. Additionally, servicing calls canmore easily be grouped based on location because the administrator canidentify devices in need of servicing in proximity to one another.

FIGS. 3A-B show exemplary screen shots for providing information aboutthe status of medical equipment to an administrator of the medicalequipment. As shown in FIG. 3A, a user interface 300 includes a devicemanagement status table. The status table includes a status column 302that displays summary level status information for medical equipmentgrouped by location. The location is displayed in location column 304and, if multiple sites exist for a particular location, a site number isdisplayed in site column 306. Thus, user interface 300 provides summarylevel information about medical equipment grouped by location (e.g., asshown in rows 308, 310, 312, 314, 316). For example, if multiple unitsof medical equipment exist at any particular geographic area (e.g.,multiple devices in a particular building, such as building 202 and FIG.2), the status information relays a summarized status of the medicalequipment for the selected area. In some examples, the status displayedis the lowest status (e.g., worst) of all of the medical equipmentassociated with the location. For example, if a location included 10medical equipment with one being nonfunctional, two being functional butin need of routine servicing, and seven devices that are fullyfunctional, the status displayed in status column 302 would indicate anonfunctional device.

The status can be displayed as color-coded icons associated with eachpiece of medical equipment where the color coding is indicative of thestatus. For example as shown in FIG. 3A, the entries in the statuscolumn 302 can be color-coded to indicate whether the equipment is fullyfunctional. In one particular example, a green color coding of the iconcould be representative of equipment that has recently been tested andis fully functional, a red color coding can be representative ofequipment that is not fully functional, and a yellow color coding couldbe representative of equipment that has not recently been tested but waspreviously functional at the time of the last test and/or representativeof equipment that is in need of routine servicing. In the particularexample shown in row 308, devices associated with the Chelmsfordlocation are color-coded as red to indicate that one or more of theassociated medical devices in that location is not functional.

FIG. 3B shows a user interface 330 for providing device level statusinformation for medical equipment. User interface 330 can be displayedbased on a user's selection of a particular grouped location from userinterface 300. For example, clicking on a link in row 308 in userinterface 300 can produce user interface 330, which provides devicelevel status information for the devices at the selected location (e.g.,the Chelmsford location). The device level status information shown inuser interface 330 can include a status column 336, location column 338,self-test results column 340, error identification column 342, andserial number column 344. The status column 336 can include statusinformation for a particular device. The status information can besimilar to the status information described above. The location column338 includes details of the location for the particular piece of medicalequipment. For example, the location could include an address and/or alocation within a building. This location is specific to the particulardevice as opposed to being a generalized group location as shown in FIG.3A. The self-test results column 340 includes information about whetherthe medical equipment has passed or failed a self-test and/or an optionto initiate a test of the device. Additionally, in some examples, theself-test results column 340 would include information about the date ofthe most recent self-test. The error column 342 includes informationabout why a device has failed a self-test and/or servicing needed forthe device. The serial number column 344 includes a serial number forthe medical equipment such that the medical equipment can be identifiedby the administrator.

Allowing an administrator to view status information for each of thedevices at a particular location can provide the administrator withinformation about why devices are not functioning and/or what issuescould be addressed during a single servicing call. For example, if anadministrator is making a service call to the Chelmsford location toservice the nonfunctional device, the administrator can additionallyview the status of other devices and service those devices at the sametime. In the particular example of FIG. 3B, while servicing the deviceon the second floor west stairwell (e.g., shown in row 334) theadministrator could additionally replace the electrodes in the device onthe first floor reception (e.g., as shown in row 332). Additionally,identification of an error (e.g., shown in column 336) that has resultedin the status of the medical equipment can help the administrator toprepare for the needed servicing.

In some examples, the location grouping (e.g., as shown in FIG. 3A) canbe modified by a user to change the grouping to include devices locatedwithin a larger or smaller geographic area. For example, a user couldselect from viewing location based on city, zip code, building,neighborhood, company, or user-defined geographic regions. Allowing auser to select and change the size of the location used to group medicalequipment when displaying their status can enable an administrator tomore effectively service the devices. For example, in a majormetropolitan area medical equipment such as defibrillators could bedensely located such that displaying status information on a citywidelevel would provide little assistance to an administrator when trying toplan for servicing calls (e.g., displaying defibrillators in Bostoncould result in thousands of defibrillators). In such a situation, theadministrator could narrow the geographic extent used to group themedical equipment, such that fewer medical equipment are associated witheach location.

FIG. 4 is a flow chart of a process 400 for providing status informationabout automated external defibrillators (AEDs). While process 400 isdescribed herein as providing status information about AEDs, thisprocess could additionally and/or alternatively be applied to othertypes of medical equipment. AEDs send status information to a medicalequipment management system 216. The medical equipment management system216 receives the status updates from the AEDs (402). The medicalequipment management system 216 stores the status updates in acentralized database (404). For example, the medical equipmentmanagement center can include a database of AEDs and information aboutthe status associated with each AED can be updated based on the receivedstatus updates.

The medical equipment management system 216 receives a login requestfrom an AED administrator (406). Based on the authentication of theadministrator, the medical equipment management system 216 determinesAED devices for which the administrator should be granted access (408).For example, in the database that includes the information about theAEDs and their status, each AED may be associated with one or moreadministrators who are allowed access to the status of the AEDs. Afterdetermining a set of AEDs for which the user has access, the medicalequipment management system 216 groups the AEDs by location (410). Forexample, the medical equipment management system 216 can group the AEDsby city, neighborhood, building, or another measure of geographicproximity. The medical equipment management system 216 displays the listof AED locations and status information for each location to the user(412). As noted above, the status information is indicative of a statusfor the multiple devices associated with in the location. For example,the status information can display the lowest or worst status of alldevices within the location. In another example, the status informationcould include a percentage of devices included in the group for thelocation having each of a plurality of different statuses. For example,if the system provided three statuses of red, yellow, and green (asdescribed above), then the system could display the percentage of AEDsfalling into each of the color-coded categories.

While location level summary information about the status of the AEDsincluded in the location can be beneficial, and some situations anadministrator may desire to see information on a device level ratherthan a location level. The medical equipment management system 216determines whether a request for device specific information has beenreceived (414). For example, referring back to FIG. 3A, a user canrequest to view device specific information for a location by clickingon one of the rows in the displayed status information table. Inresponse to receiving a request for device specific information, themedical equipment management system displays a list of individual AEDsand their associated status information (418). For example, device levelinformation such as the information shown in FIG. 3B can be provided tothe user. If a request for the device level information is not received,the system exits the process (416).

As noted above, over time software for the defibrillators or othermedical equipment may be updated based on enhancements or changes toprotocols and/or configurations for the defibrillator may be modified.The medical equipment management system 216 can provide a centralizedaccess and management tool for updating software and or configurationsfor remotely located medical equipment such as AEDs. By providing acentral server that has information about currently stored software andconfigurations and the ability to push software and configurationchanges to remotely located medical equipment, the software andconfigurations for medical equipment can more easily be kept up to dateas changes are promulgated.

FIG. 5 is an exemplary screen shot for identifying medical equipment forwhich the software update and/or configuration update is available, andsending information to update the medical device. Similar to the devicemanagement user interface 300 shown in FIG. 3A, user interface 500includes a table with a status column 502, location column 504 and sitecolumn 506. In addition to providing the status information as describedabove, the user interface 500 additionally includes an indicator appliedto entries in the table when a software and/or configuration update isavailable. For example, indicator 508 can be applied to a location whena software update is available for one or more units of medicalequipment associated with the location. A user can see additionalinformation about the available software updates by selecting thelocation to see device level information (e.g., as shown in FIG. 3B).Additionally, and/or alternatively update information could be includedin an additional column of the table.

In some examples, user interface 500 can additionally allow a user toupdate a the software and or configurations for the medical equipment.In order to update the software for the devices associated with aparticular location, and administrator can select the update all link510. If the administrator would prefer to update the devicesindividually, and update link can be included on the device specificstatus page. Selection of the software update link sends availableupdates to the medical equipment.

FIG. 6 is a flow chart of a process 600 for providing software and/orconfiguration updates to automated external defibrillators (AEDs). Whileprocess 600 is described herein as providing status information andupdating AEDs, this process could additionally and/or alternatively beapplied to other types of medical equipment. Process 600 begins with thereceipt of new or updated software and or configurations for AEDs (602).For example, changes to configurations or updates to software can bestored in a central database. The medical equipment management system216 receives a login request from an AED administrator (604).

Based on the authentication of the administrator, the medical equipmentmanagement system 216 determines AED devices for which the administratorshould be granted access (606). For example, in the database thatincludes the information about the AEDs and their status, each AED maybe associated with one or more administrators who are allowed access tothe status of the AEDs and push updates to the AEDs. For the devicesidentified as being associated with the administrator, the medicalequipment management system determines whether the software and orconfiguration updates are relevant to the determined set of AEDs. Forexample, current configurations or software versions for the AEDs can becompared to a list of available updates to see if the most recentconfigurations and software are stored on the AEDs. The software andconfigurations available for a particular AED may be based on a make ormodel of the AED. For example, some software updates may only beavailable to a subset of AED models. In some examples, software updatesand configuration updates can be associated with model numbers and witha timestamp of when the software update or configuration update wasprovided. Using this information, stored device models and a time of thelast update for a particular device can be used to determine whetherconfiguration or software updates are available for the device. Themedical equipment management system 216 displays to the user, a list ofAEDs including which AEDs have software and or configuration updatesavailable. For example, the medical equipment management system 212 cansend information to a user device to cause the user device to displaysuch a list. The list can be grouped by location, for example, asdescribed above. A user can update the software or configurations on oneor more of the AEDs by selecting a link to send the update to the AED.Based on the user entered request for update, the medical equipmentmanagement system 212 receives the request to update software, and/orconfigurations for a particular AED (not shown) or for all AEDsassociated with a particular location (612). Based on the receivedrequest, the medical equipment management system 212 sends the softwareand/or configuration update to the selected AED device or group of AEDdevices (614). Thus, the administrator can update the software and/orconfigurations for a particular AED device or group of AED devices froma central location.

FIG. 7 shows an example of a generic computer device 700 and a genericmobile computer device 750, which may be used with the techniquesdescribed here. Generic computer device 700 can be used to provide theabove described functionality of the medical equipment management system212. Computing device 700 is intended to represent various forms ofdigital computers, such as laptops, desktops, workstations, personaldigital assistants, servers, blade servers, mainframes, and otherappropriate computers. Generic mobile computer device 750 can be acomputing component of defibrillator 112 or can be a laptop computersuch as laptop computer 116. Computing device 750 is intended torepresent various forms of mobile devices, such as personal digitalassistants, cellular telephones, smartphones, and other similarcomputing devices that can receive information from a defibrillator 112and provide that information to another computing device such ascomputer device 700. The components shown here, their connections andrelationships, and their functions, are meant to be exemplary only, andare not meant to limit implementations of the inventions describedand/or claimed in this document.

Computing device 700 includes a processor 702, memory 704, a storagedevice 706, a high-speed interface 708 connecting to memory 704 andhigh-speed expansion ports 710, and a low speed interface 712 connectingto low speed bus 714 and storage device 706. Each of the components 702,704, 706, 708, 710, and 712, are interconnected using various busses,and may be mounted on a common motherboard or in other manners asappropriate. The processor 702 can process instructions for executionwithin the computing device 700, including instructions stored in thememory 704 or on the storage device 706 to display graphical informationfor a GUI on an external input/output device, such as display 716coupled to high speed interface 708. In other implementations, multipleprocessors and/or multiple buses may be used, as appropriate, along withmultiple memories and types of memory. Also, multiple computing devices700 may be connected, with each device providing portions of thenecessary operations (e.g., as a server bank, a group of blade servers,or a multi-processor system).

The memory 704 stores information within the computing device 700. Inone implementation, the memory 704 is a volatile memory unit or units.In another implementation, the memory 704 is a non-volatile memory unitor units. The memory 704 may also be another form of computer-readablemedium, such as a magnetic or optical disk.

The storage device 706 is capable of providing mass storage for thecomputing device 700. In one implementation, the storage device 706 maybe or contain a computer-readable medium, such as a floppy disk device,a hard disk device, an optical disk device, or a tape device, a flashmemory or other similar solid state memory device, or an array ofdevices, including devices in a storage area network or otherconfigurations. A computer program product can be tangibly embodied inan information carrier. The computer program product may also containinstructions that, when executed, perform one or more methods, such asthose described above. For example, the computer program product maycontain instructions for receiving status information from anddisplaying status information for various medical devices such as AEDs.The information carrier is a computer- or machine-readable medium, suchas the memory 704, the storage device 706, or memory on processor 702.

The high speed controller 708 manages bandwidth-intensive operations forthe computing device 700, while the low speed controller 712 manageslower bandwidth-intensive operations. Such allocation of functions isexemplary only. In one implementation, the high-speed controller 708 iscoupled to memory 704, display 716 (e.g., through a graphics processoror accelerator), and to high-speed expansion ports 710, which may acceptvarious expansion cards (not shown). In the implementation, low-speedcontroller 712 is coupled to storage device 706 and low-speed expansionport 714. The low-speed expansion port, which may include variouscommunication ports (e.g., USB, Bluetooth, Ethernet, wireless Ethernet)may be coupled to one or more input/output devices, such as a keyboard,a pointing device, a scanner, or a networking device such as a switch orrouter, e.g., through a network adapter.

The computing device 700 (e.g., management system 216) may beimplemented in a number of different forms, as shown in the figure. Forexample, it may be implemented as a standard server 720, or multipletimes in a group of such servers. It may also be implemented as part ofa rack server system 724. In addition, it may be implemented in apersonal computer such as a laptop computer 722. Alternatively,components from computing device 700 may be combined with othercomponents in a mobile device (not shown), such as device 750. Each ofsuch devices may contain one or more of computing device 700, 750, andan entire system may be made up of multiple computing devices 700, 750communicating with each other.

Computing device 750 provides information about the status of medicalequipment such as an AED to management system 216 (e.g., to computingdevice 700) and includes a processor 752, memory 764, and aninput/output device such as a display 754, a communication interface766, and a transceiver 768, among other components. The device 750 mayalso be provided with a storage device, such as a microdrive or otherdevice, to provide additional storage. Each of the components 750, 752,764, 754, 766, and 768, are interconnected using various buses, andseveral of the components may be mounted on a common motherboard or inother manners as appropriate. In some examples, computing device 750 isincluded in an AED such as AED 112 shown in FIG. 1.

The processor 752 can execute instructions within the computing device750, including instructions stored in the memory 764. For example, theprocessor 752 can execute instructions to perform a self-test on a pieceof medical equipment and forward the results to the central managementsystem 216. The processor may be implemented as a chipset of chips thatinclude separate and multiple analog and digital processors. Theprocessor may provide, for example, for coordination of the othercomponents of the device 750, such as control of user interfaces,applications run by device 750, and wireless communication by device750.

Processor 752 may communicate with a user through control interface 758and display interface 756 coupled to a display 754. The display 754 maybe, for example, a TFT LCD (Thin-Film-Transistor Liquid Crystal Display)or an OLED (Organic Light Emitting Diode) display, or other appropriatedisplay technology. The display interface 756 may comprise appropriatecircuitry for driving the display 754 to present graphical and otherinformation to a user. The control interface 758 may receive commandsfrom a user and convert them for submission to the processor 752. Inaddition, an external interface 762 may be provide in communication withprocessor 752, so as to enable near area communication of device 750with other devices. External interface 762 may provide, for example, forwired communication in some implementations, or for wirelesscommunication in other implementations, and multiple interfaces may alsobe used.

The memory 764 stores information within the computing device 750. Thememory 764 can be implemented as one or more of a computer-readablemedium or media, a volatile memory unit or units, or a non-volatilememory unit or units. Expansion memory 774 may also be provided andconnected to device 750 through expansion interface 772, which mayinclude, for example, a SIMM (Single In Line Memory Module) cardinterface. Such expansion memory 774 may provide extra storage space fordevice 750, or may also store applications or other information fordevice 750. Specifically, expansion memory 774 may include instructionsto carry out or supplement the processes described above, and mayinclude secure information also. Thus, for example, expansion memory 774may be provide as a security module for device 750, and may beprogrammed with instructions that permit secure use of device 750. Inaddition, secure applications may be provided via the SIMM cards, alongwith additional information, such as placing identifying information onthe SIMM card in a non-hackable manner.

The memory may include, for example, flash memory and/or NVRAM memory,as discussed below. In one implementation, a computer program product istangibly embodied in an information carrier. The computer programproduct contains instructions that, when executed, perform one or moremethods, such as those described above. The information carrier is acomputer- or machine-readable medium, such as the memory 764, expansionmemory 774, or memory on processor 752.

Device 750 may communicate wirelessly through communication interface766, which may include digital signal processing circuitry wherenecessary. Communication interface 766 may provide for communicationsunder various modes or protocols, such as GSM voice calls, SMS, EMS, orMMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, among others.Such communication may occur, for example, through radio-frequencytransceiver 768. In addition, short-range communication may occur, suchas using a Bluetooth, WiFi, or other such transceiver (not shown). Inaddition, GPS (Global Positioning System) receiver module 770 mayprovide additional navigation- and location-related wireless data todevice 750, which may be used as appropriate by applications running ondevice 750. This communication via communication interface 766 canprovide status information about the associated medical equipment to themanagement system 216 (e.g., to computing device 700).

Device 750 may also communicate audibly using audio codec 760, which mayreceive spoken information from a user and convert it to usable digitalinformation. Audio codec 760 may likewise generate audible sound for auser, such as through a speaker, e.g., in a handset of device 750. Suchsound may include sound from voice telephone calls, may include recordedsound (e.g., voice messages, music files, etc.) and may also includesound generated by applications operating on device 750.

The computing device 750 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as acellular telephone 780. It may also be implemented as part of a,personal digital assistant, or other similar mobile device. It may alsobe implemented as part of a AED 783, or other medical equipment. It mayalso be implemented as part of a laptop computer such as computer 116 inFIG. 1.

Various implementations of the systems and techniques described here canbe realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations can include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device.

These computer programs (also known as programs, software, softwareapplications or code) include machine instructions for a programmableprocessor, and can be implemented in a high-level procedural and/orobject-oriented programming language, and/or in assembly/machinelanguage. As used herein, the terms “machine-readable medium”“computer-readable medium” refers to any computer program product,apparatus and/or device (e.g., magnetic discs, optical disks, memory,Programmable Logic Devices (PLDs)) used to provide machine instructionsand/or data to a programmable processor, including a machine-readablemedium that receives machine instructions as a machine-readable signal.The term “machine-readable signal” refers to any signal used to providemachine instructions and/or data to a programmable processor.

A number of embodiments have been described. Nevertheless, it will beunderstood that various modifications may be made without departing fromthe spirit and scope of the invention.

In addition, the logic flows depicted in the figures do not require theparticular order shown, or sequential order, to achieve desirableresults. In addition, other steps may be provided, or steps may beeliminated, from the described flows, and other components may be addedto, or removed from, the described systems. Accordingly, otherembodiments are within the scope of the following claims. Many otherimplementations of the invention other than those described above arewithin the invention, which is defined by the following claims.

What is claimed is:
 1. A method comprising receiving status updates frommultiple automated external defibrillators; receiving, from a user, arequest to access status information; and sending, to the user, summarylevel status information for at least some of the multiple automatedexternal defibrillators, the summary level status information beinggrouped based on a measure of geographic proximity of the multipleautomated external defibrillators.
 2. The method of claim 1, furthercomprising: receiving a selection of a location; and displaying statusinformation for individual automated external defibrillators associatedwith the location.
 3. The method of claim 1, wherein sending summarylevel status information grouped based on a measure of geographicproximity comprises sending summary level status information groupedbased on the city in which the automated external defibrillator islocated.
 4. The method of claim 1, wherein sending summary level statusinformation grouped based on a measure of geographic proximity comprisessending summary level status information grouped based on a building inwhich the automated external defibrillator is located.
 5. The method ofclaim 1, further comprising grouping the automated externaldefibrillators based on a geographic location of the automated externaldefibrillators.
 6. The method of claim 1, further comprising determininga subset of automated external defibrillators based on an identity ofthe user and access information for the automated externaldefibrillators.
 7. The method of claim 1, wherein the status informationfurther comprises information about available software updates and themethod further comprises sending instructions to cause an automatedexternal defibrillator to perform at least one of automaticallyinstalling a software update and updating a configuration.
 8. A computerprogram product comprising instructions to cause a processor to: receivestatus updates from multiple automated external defibrillators; receivea request to access status information; and send summary level statusinformation for at least some of the multiple automated externaldefibrillators, the summary level status information being grouped basedon a measure of geographic proximity of the multiple automated externaldefibrillators.
 9. The computer program product of claim 8, furthercomprising instructions to cause the processor to: receive a selectionof a location; and display status information for individual automatedexternal defibrillators associated with the location.
 10. The computerprogram product of claim 8, wherein the instructions to send summarylevel status information grouped based on a measure of geographicproximity comprise instructions to send summary level status informationgrouped based on the city in which the automated external defibrillatoris located.
 11. The computer program product of claim 8, wherein theinstructions to send summary level status information grouped based on ameasure of geographic proximity comprise instructions to send summarylevel status information grouped based on a building in which theautomated external defibrillator is located.
 12. The computer programproduct of claim 8, further comprising instructions to cause theprocessor to group the automated external defibrillators based on ageographic location of the automated external defibrillators.
 13. Thecomputer program product of claim 8, further comprising instructions tocause the processor to determine a subset of automated externaldefibrillators based on an identity of the user and access informationfor the automated external defibrillators.
 14. The computer programproduct of claim 8, wherein the status information further comprisesinformation about available software updates and the method furthercomprises sending instructions to cause an automated externaldefibrillator to perform at least one of automatically installing asoftware update and updating a configuration.
 15. A system comprising: adatabase that includes status information for emergency responseequipment; a computer configured to: receive status updates frommultiple automated external defibrillators; store the status updates inthe database; receive a request to access status information; and sendsummary level status information for at least some of the multipleautomated external defibrillators, the summary level status informationbeing grouped based on a measure of geographic proximity of the multipleautomated external defibrillators.
 16. The system of claim 15, whereinthe computer is further configured to: receive a selection of alocation; and display status information for individual automatedexternal defibrillators associated with the location.
 17. The system ofclaim 15, wherein the instructions to send summary level statusinformation grouped based on a measure of geographic proximity compriseinstructions to send summary level status information grouped based onthe city in which the automated external defibrillator is located. 18.The system of claim 15, wherein the instructions to send summary levelstatus information grouped based on a measure of geographic proximitycomprise instructions to send summary level status information groupedbased on a building in which the automated external defibrillator islocated.
 19. The system of claim 15, further comprising instructions tocause the processor to group the automated external defibrillators basedon a geographic location of the automated external defibrillators. 20.The system of claim 15, wherein the status information further comprisesinformation about available software updates and the method furthercomprises sending instructions to cause an automated externaldefibrillator to automatically perform at least one of installing asoftware update and updating a configuration.